|
|
|
|
|
|
|
Figure 9.1.
Subsystem control classes for an order processing
application. |
|
|
|
|
|
|
|
|
Figure 9.2.
Subsystems implemented as components. |
|
|
|
|
|
|
|
|
Candidate Subsystems for the Samsona Bank Teller System Example |
|
|
|
|
|
|
|
|
Your client, the Second Bank of Carrollton, is quite pleased with the progress you're making with the bank teller system. You've shown her and her staff prototypes at the expected milestone dates, even though the code behind the scenes was ugly in many places. You and your staff developers told yourselves that you'd organize the code later when the design models stabilize. |
|
|
|
|
|
|
|
|
Well, that time has come. Adding code increment by increment to the application has become more and more complex and disorganized. At the same time, your team of designers has elaborated the interaction and class diagrams to a point that accurate low-level details are stable enough to be implemented in Visual Basic code. As the chief architect, you also realize that some of the modifications in the application's architectural |
|
|
|
|
|
